Add daemon process#1732
Merged
Merged
Conversation
The daemon process is a wrapper around the actual Bazaar application, it's responsibilities are managing the application, forwarding launches with parameters (except --no-window) and implementing the search provider (also auto-updates in the future). The search provider part consumes a ~2mb file with the data needed for the search engine, its generated after the entry-group cache. The daemon does not link to gobject library to keep the memory footprint as low as possible, around 8 mb with a further 12mb for Flatpak stuff
Collaborator
ferret.mp4 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The daemon process is a wrapper around the actual Bazaar application, it's responsibilities are managing the application, forwarding launches with parameters (except --no-window) and implementing the search provider (also auto-updates in the future).
The search provider part consumes a ~2mb file with the data needed for the search engine, its generated after the entry-group cache.
The daemon does not link to gobject library to keep the memory footprint as low as possible, around 8 mb with a further 12mb for Flatpak stuff. I believe the recent improvements with launch speeds it makes sense to not keep the main application alive, especially when RAM is so expensive nowadays...
You will have to reinstall the Flatpak app to test everything out properly